\b0 method of NXEPSImageRep seems to change the current transformation matrix (CTM). When does this happen, and is it a bug?\
\
A: Some of the
\b drawIn:
\b0 and
\b drawAt:
\b0 methods in the various NXImageRep subclasses are documented as changing the transformation matrix. They do this without restoring the original matrix, leaving it to the developer to determine if they need to put a
\b gsave/grestore
\b0 pair around their call.\
\
The NXEPSImageRep
\b draw
\b0 method is not documented as changing the CTM; however, if the origin of the bounding box in the EPS file is not 0,0, this method will cause a
\b translate
\b0 . Thus this method might also need to be protected with a
\b gsave/grestore
\b0 pair.\
\
For 2.0 and any compatible release after that, it's probably safest to assume that the
\b draw
\b0 ,
\b drawIn:
\b0 , and
\b drawAt:
\b0 methods can change the CTM; thus developers should restore it if they need to rely on it after the method returns.\